This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
RE: Clustering v9 Meetings with standalone WAS HTTP Proxy ~Yentl Zekresachek 16.Sep.14 06:20 AM a Web browser General 9.0Windows
Thanks as always for your response.
The reason we only have one WAS Proxy is we are starting the rollout – the plan is to have two WAS Proxies and use a load balancer. This design means that if Meetings1 fails you will be failed over to Meeting2 by the WAS Proxy whereas if you are connected to a WAS Proxy on Meetings1 you will not be failed over as the server is unavailable.
I can see that having the WAS Proxy on the servers themselves would be easier. And yes we have Virtual Hosts for all three servers. Currently the primary node has three servers running but the secondary only has meetings currently active as we ran into this issue and stopped installing.
I think the issue is hostnames in DNS and the server names used to install the components. Something is not correct.
We have this setup:
Primary Node: server002.company.com : 10.0.0.1
DNS Aliases: stadvanced.company.com - Port 80 is default_port for advanced;
Servers: SSC (server002.company.com), Meetings (meetings.company.com), ST Proxy (webchat.company.com), Advanced (stadvanced.company.com)
Local Hosts File entries for meetings.company.com and webchat.company.com to 10.0.0.1
Issue here is that meetingscompany.com points to the WAS Proxy in DNS but is installed as the server name and host alias name for meetings on the primary. The WAS Proxy is installed as webmeetingscompany.com. I’ve since created a Host Alias for webmeetings company.com which works to attend meetinsg if I only have one of the two clustered servers running !
WAS Proxy Node: server004.company.com : 10.0.0.3
DNS Aliases: meetings.company.com; webmeetings.company.com, webchat.company.com
Servers: WAS Proxy (installed as webmeetings.company.com which can be used to attend a meeting via the Host Aliases now created.
Return to top
. . . . RE: Clustering v9 Meetings with sta... (~Evelyn Asagero... 16.Sep.14) 
Print this page
